🌎 rns.kin.earth git 🌍
Commit eff0c91ed0e6ef7488198db312813bf0ec7dcf63
Parents : dba6cd8
Author : Mark Qvist <mark@unsigned.io>
Date : 2025-04-16T00:35:56+02:00
Updated docs
Changes
2 files changed, 24 insertions(+), 8 deletions(-)
Diff
diff --git a/README.md b/README.md
index 3b0ac70b..4fa24c7b 100755
--- a/README.md
+++ b/README.md
@@ -312,7 +312,15 @@ organisation? Make them a reality quickly by sponsoring their implementation.
## Cryptographic Primitives
Reticulum uses a simple suite of efficient, strong and well-tested cryptographic
primitives, with widely available implementations that can be used both on
-general-purpose CPUs and on microcontrollers. The utilised primitives are:
+general-purpose CPUs and on microcontrollers.
+
+One of the primary considerations for choosing this particular set of primitives is
+that they can be implemented *safely* and with relatively few pitfalls, on practically
+all current computing platforms.
+
+The primitives listed here *are authoritative*. Anything claiming to be Reticulum,
+but not using these exact primitives **is not** Reticulum, and possibly an
+intentionally compromised or weakened clone. The utilised primitives are:
- Reticulum Identity Keys are 512-bit Curve25519 keysets
- A 256-bit Ed25519 key for signatures
@@ -320,9 +328,9 @@ general-purpose CPUs and on microcontrollers. The utilised primitives are:
- HKDF for key derivation
- Encrypted tokens are based on the [Fernet spec](https://github.com/fernet/spec/)
- Ephemeral keys derived from an ECDH key exchange on Curve25519
- - AES-128 in CBC mode with PKCS7 padding
- HMAC using SHA256 for message authentication
- - IVs are generated through os.urandom()
+ - IVs must be generated through `os.urandom()` or better
+ - AES-128 or AES-256 in CBC mode with PKCS7 padding
- No Fernet version and timestamp metadata fields
- SHA-256
- SHA-512
diff --git a/docs/source/understanding.rst b/docs/source/understanding.rst
index 31e32c9e..60ce283d 100644
--- a/docs/source/understanding.rst
+++ b/docs/source/understanding.rst
@@ -858,9 +858,17 @@ of the different interface modes, and how they are configured.
Cryptographic Primitives
------------------------
-Reticulum has been designed to use a simple suite of efficient, strong and modern
-cryptographic primitives, with widely available implementations that can be used
-both on general-purpose CPUs and on microcontrollers. The necessary primitives are:
+Reticulum uses a simple suite of efficient, strong and well-tested cryptographic
+primitives, with widely available implementations that can be used both on
+general-purpose CPUs and on microcontrollers.
+
+One of the primary considerations for choosing this particular set of primitives is
+that they can be implemented *safely* and with relatively few pitfalls, on practically
+all current computing platforms.
+
+The primitives listed here *are authoritative*. Anything claiming to be Reticulum,
+but not using these exact primitives **is not** Reticulum, and possibly an
+intentionally compromised or weakened clone. The utilised primitives are:
* Ed25519 for signatures
@@ -872,11 +880,11 @@ both on general-purpose CPUs and on microcontrollers. The necessary primitives a
* Ephemeral keys derived from an ECDH key exchange on Curve25519
- * AES-128 in CBC mode with PKCS7 padding
+ * AES-128 or AES-256 in CBC mode with PKCS7 padding
* HMAC using SHA256 for message authentication
- * IVs are generated through os.urandom()
+ * IVs must be generated through ``os.urandom()`` or better
* No Fernet version and timestamp metadata fields
Served by rngit 1.5.2 - Generated in 0.05s